Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ECO-5009][CHA-RL1] Room ATTACH #27

Closed
wants to merge 24 commits into from
Closed

[ECO-5009][CHA-RL1] Room ATTACH #27

wants to merge 24 commits into from

Conversation

sacOO7
Copy link

@sacOO7 sacOO7 commented Oct 3, 2024

Fixed #21

Copy link

coderabbitai bot commented Oct 3, 2024

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@sacOO7 sacOO7 changed the title Added checks for current room state before room ATTACH operation Feature - Room ATTACH Oct 3, 2024
@sacOO7 sacOO7 changed the title Feature - Room ATTACH [ECO-5009][CHA-RL1]Feature - Room ATTACH Oct 3, 2024
@sacOO7 sacOO7 changed the title [ECO-5009][CHA-RL1]Feature - Room ATTACH [ECO-5009][CHA-RL1 Room ATTACH Oct 3, 2024
@sacOO7 sacOO7 changed the title [ECO-5009][CHA-RL1 Room ATTACH [ECO-5009][CHA-RL1] Room ATTACH Oct 3, 2024
# Conflicts:
#	chat-android/src/main/java/com/ably/chat/RoomOptions.kt
#	chat-android/src/main/java/com/ably/chat/RoomStatus.kt
…ributor

across all contributors and initialized RoomLifeCycle inside Room
attach method to call lifecyclemanager attach method instead
@@ -3,105 +3,106 @@ package com.ably.chat
/**
* Error codes for the Chat SDK.
*/
object ErrorCodes {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do you think enum here is better?

Copy link
Author

@sacOO7 sacOO7 Nov 8, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Having type for given ErrorCode enforces compile time check for right assertions with reusability.
Also, IDE gives proper suggestions when matching error codes, unlike when it's generic Int.
This makes it easy to write ErrorCode assertions in code as well as tests.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, in chat-js, ErrorCode is represented as an enum, this makes it super easy to correlate between two codebases.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure I understand, could you give an example? Typescript's enums are nothing like Kotlin's enums. Error codes usually come from backend, and they come as Int. I currently don't understand what benefits we get, except we have to additionally serialize/deserialize Int into enum

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, I am closing this PR in favor of #33. We can continue discussion for the same there 👍

@@ -118,3 +162,60 @@ data class RoomStatusChange(
*/
val error: ErrorInfo? = null,
)

open class RoomStatusEvenEmitter : EventEmitter<RoomLifecycle, RoomStatus.Listener>() {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

here is typo in the name, should be ...EventEmitter

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed ce9c0ba

}
}

class DefaultStatus(private val logger: LogHandler?) : InternalRoomStatus, RoomStatusEvenEmitter() {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not Kotlin idiomatic to use inheritance here. It's much better to use composition

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed ce9c0ba

Refactored DefaultStatus, using composition over inheritance for RoomStatusEventEmitter
# Conflicts:
#	chat-android/src/main/java/com/ably/chat/RoomReactions.kt
@sacOO7
Copy link
Author

sacOO7 commented Nov 8, 2024

Superseded by #33

@sacOO7 sacOO7 closed this Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[CHA-RL1] Implement Room ATTACH operation
2 participants